What is the purpose of the change?

This PR stabilizes propertyconfigurer-related tests inside dubbo-config-spring that were intermittently failing under randomized execution orders (NonDex) due to shared Dubbo/Spring framework state leaking across test boundaries. The following tests were consistently among the flaky failures before this fix, but now pass reliably across all NonDex seeds:

• PropertyConfigurerTest: testEarlyInit
• PropertySourcesConfigurerTest: testEarlyInit
• PropertySourcesInJavaConfigTest: testImportPropertySource, testCustomPropertySourceBean

Root Cause

These failures are identical to previously fixed issues in:

• Fix: Stabilize ExporterSideConfigUrlTest by disabling metrics initialization during URL export #15778
• Stabilize MethodConfigTest by disabling metrics initialization to avoid Micrometer nondeterminism #15782
• Fix: Stabilize multiple tests in ServiceConfigTest by isolating system properties and cached state #15785

Each of those PRs addressed flakiness caused by Micrometer’s CompositeMeterRegistry, which can throw an ArrayIndexOutOfBoundsException when it iterates over internal IdentityHashMap structures under randomized execution orders (NonDex).

The tests mentioned above suffered from the same underlying issue:
Dubbo framework state was leaking between test methods. This meant that the behavior of reference creation in one test could affect subsequent tests, causing nondeterministic failures.

Changes Made

To fully isolate each test method and eliminate shared state, the following changes were applied:

• Disabled the metrics subsystem at the beginning of each test.
• Cleared all system properties via SysProps.clear() in the lifecycle hooks to avoid cross-test pollution.
• Reset framework state using DubboBootstrap.reset() to ensure isolation between tests.

Verification

You can try running the following snippet of code from the dubbo repo root, on both pre-fix and post-fix code

./mvnw -q -pl dubbo-config/dubbo-config-spring \
  edu.illinois:nondex-maven-plugin:2.2.1:nondex \
  -DnondexRuns=50

The tests should fail intermittently on the pre-fix version, but pass consistently across all seeds on the post-fix version.
NonDex run logs will be available under the dubbo-config/dubbo-config-spring/.nondex directory.

Checklist

• Make sure there is a GitHub_issue field for the change.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit-test to verify your logic correction. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Make sure gitHub actions can pass. Why the workflow is failing and how to fix it?